Skip to content

feat(nextjs): Support native debugIds in turbopack #17853

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 8 commits into from
Oct 14, 2025
Merged

feat(nextjs): Support native debugIds in turbopack #17853

merged 8 commits into from
Oct 14, 2025
+409 −41

Conversation

chargome
Copy link
Member

@chargome chargome commented Oct 2, 2025 •
edited
Loading

Adds support for vercel/next.js#84319

  • Switches to automatically injecting native debug Ids whenever the Next.js version supports it
  • Updates core functionality on supporting sentryDebugId alongside the more generic debugId that Vercel uses.
  • Something to consider: We write both sentryDebugIds and debugIds into the cache but since we generate them in this order, debugIds will have precedence when there is a bundle with both keys in it.

closes #17841

@chargome chargome self-assigned this Oct 2, 2025
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Oct 3, 2025 •
edited
Loading

size-limit report 📦

Path Size % Change Change
@sentry/browser 24.48 kB +0.3% +72 B 🔺
@sentry/browser - with treeshaking flags 22.96 kB +0.27% +60 B 🔺
@sentry/browser (incl. Tracing) 40.67 kB +0.14% +54 B 🔺
@sentry/browser (incl. Tracing, Replay) 79.03 kB +0.07% +51 B 🔺
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 68.69 kB +0.11% +71 B 🔺
@sentry/browser (incl. Tracing, Replay with Canvas) 83.72 kB +0.07% +53 B 🔺
@sentry/browser (incl. Tracing, Replay, Feedback) 95.9 kB +0.09% +80 B 🔺
@sentry/browser (incl. Feedback) 41.17 kB +0.18% +70 B 🔺
@sentry/browser (incl. sendFeedback) 29.14 kB +0.26% +75 B 🔺
@sentry/browser (incl. FeedbackAsync) 34.05 kB +0.23% +76 B 🔺
@sentry/react 26.19 kB +0.3% +76 B 🔺
@sentry/react (incl. Tracing) 42.62 kB +0.16% +68 B 🔺
@sentry/vue 28.99 kB +0.27% +76 B 🔺
@sentry/vue (incl. Tracing) 42.44 kB +0.13% +55 B 🔺
@sentry/svelte 24.51 kB +0.3% +71 B 🔺
CDN Bundle 26.7 kB +0.24% +63 B 🔺
CDN Bundle (incl. Tracing) 41.22 kB +0.19% +76 B 🔺
CDN Bundle (incl. Tracing, Replay) 77.53 kB +0.11% +82 B 🔺
CDN Bundle (incl. Tracing, Replay, Feedback) 82.98 kB +0.09% +74 B 🔺
CDN Bundle - uncompressed 78.33 kB +0.2% +150 B 🔺
CDN Bundle (incl. Tracing) - uncompressed 122.33 kB +0.13% +147 B 🔺
CDN Bundle (incl. Tracing, Replay) - uncompressed 237.49 kB +0.07% +147 B 🔺
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 250.25 kB +0.06% +147 B 🔺
@sentry/nextjs (client) 44.71 kB +0.16% +70 B 🔺
@sentry/sveltekit (client) 41.05 kB +0.18% +73 B 🔺
@sentry/node-core 50.8 kB +0.14% +66 B 🔺
@sentry/node 154.41 kB +0.04% +52 B 🔺
@sentry/node - without tracing 92.67 kB +0.09% +83 B 🔺
@sentry/aws-serverless 106.38 kB +0.06% +58 B 🔺

View base workflow run

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Oct 3, 2025 •
edited
Loading

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario Requests/s % of Baseline Prev. Requests/s Change %
GET Baseline 11,304 - 9,063 +25%
GET With Sentry 1,522 13% 1,396 +9%
GET With Sentry (error only) 7,494 66% 6,125 +22%
POST Baseline 1,118 - 1,208 -7%
POST With Sentry 500 45% 511 -2%
POST With Sentry (error only) 999 89% 1,045 -4%
MYSQL Baseline 3,885 - 3,293 +18%
MYSQL With Sentry 461 12% 489 -6%
MYSQL With Sentry (error only) 3,118 80% 2,726 +14%

View base workflow run

chargome
chargome commented Oct 3, 2025
View reviewed changes
Lms24
Lms24 approved these changes Oct 3, 2025
View reviewed changes
Copy link
Member

@Lms24 Lms24 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

@chargome chargome marked this pull request as ready for review October 13, 2025 11:41
@chargome chargome merged commit fd8bcbd into develop Oct 14, 2025
367 of 373 checks passed
@chargome chargome deleted the cg-nextjs-native-debug-ids branch October 14, 2025 08:24
andreiborza pushed a commit to thedanchez/sentry-javascript that referenced this pull request Oct 15, 2025
@chargome @andreiborza
feat(nextjs): Support native debugIds in turbopack (getsentry#17853)
b90e863 
Adds support for vercel/next.js#84319

- Switches to automatically injecting native debug Ids whenever the
Next.js version supports it
- Updates core functionality on supporting `sentryDebugId` alongside the
more generic `debugId` that Vercel uses.
- Something to consider: We write both `sentryDebugIds` and `debugIds`
into the cache but since we generate them in this order, `debugIds` will
have precedence when there is a bundle with both keys in it.
  
 closes getsentry#17841
@github-actions github-actions bot mentioned this pull request Oct 15, 2025
Closed
@fossabot fossabot bot mentioned this pull request Oct 15, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Lms24 Lms24 Lms24 approved these changes

Assignees

@chargome chargome

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Add support for native Debug IDs in turbopack

2 participants

@chargome @Lms24